Skip to content

fix(version): drops only-version scheme to avoid TestPyPI collisions - #23

Merged
wgordon17 merged 1 commit into
mainfrom
fix/testpypi-version-collision
Aug 19, 2026
Merged

fix(version): drops only-version scheme to avoid TestPyPI collisions#23
wgordon17 merged 1 commit into
mainfrom
fix/testpypi-version-collision

Conversation

@wgordon17

Copy link
Copy Markdown
Member

Summary

  • Drops version_scheme = "only-version" from [tool.hatch.version.raw-options], falling back to setuptools_scm's default guess-next-dev
  • Fixes TestPyPI publish failures (400 File already exists) that hit on every merge to main, since only-version pins the version to the static last tag with no per-commit distinction
  • Exact-tag release versions are unaffected; only in-between commits now get a unique .devN suffix

publish.yaml runs publish-testpypi unconditionally on every push to
main, but version_scheme = "only-version" pins the version to the
literal last tag with no per-commit distinction. Every merge to main
between tags built the identical version string, so TestPyPI rejected
the upload as a duplicate file. Dropping the override falls back to
setuptools_scm's default guess-next-dev scheme, which appends a
.devN distance suffix between tags while leaving exact-tag (release)
versions unchanged.
@wgordon17
wgordon17 marked this pull request as ready for review August 18, 2026 20:20
@wgordon17
wgordon17 requested a review from a team August 18, 2026 20:20
@wgordon17
wgordon17 merged commit 20d7e69 into main Aug 19, 2026
5 checks passed
@wgordon17
wgordon17 deleted the fix/testpypi-version-collision branch August 19, 2026 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant